Sistem Komputer: Perspektif Seorang Pemrogram (Edisi Global): Spektrum Alur Kontrol: Dari Sekuensial ke Luar Biasa

Alur kontrol standar adalah perjalanan yang dapat diprediksi: penghitung program bergerak dari alamat $a_k$ ke $a_{k+1}$ berdasarkan logika sekuensial atau lompatan eksplisit. Namun, Alur Kontrol Luar Biasa (ECF) merepresentasikan transisi "tiba-tiba" yang terjadi di luar aliran normal ini.

1. Model Matematika

Eksekusi prosesor adalah urutan $a_0, a_1, \dots, a_{n-1}$, di mana setiap $a_k$ sesuai dengan instruksi $I_k$. ECF memutus rantai ini ketika terjadi perubahan dalam status prosesor—sebuah peristiwa—memicu lompatan ke penangan khusus yang tidak ditemukan dalam jalur kode aplikasi langsung.

2. Tingkat Implementasi

ECF menghubungkan celah antara perangkat keras dan perangkat lunak. Ini berkisar dari tingkat perangkat keras pengecualian (kesalahan, interupsi) hingga tingkat sistem operasi penukaran konteks dan sinyal.

3. Realitas "Tiba-Tiba"

Baik itu pengguna menekan Ctrl+C atau panggilan sistem yang meminta akses ke disk, ECF memaksa CPU untuk melompat ke dunia yang berbeda—kernel—menjamin sistem tetap responsif terhadap perubahan status dinamis.

TERMINALbash — 80x24

> Ready. Click "Run" to execute.

Case Study: Analyzing Execution Flow in global-waitprob1.c

Synchronization and ECF Transitions

Consider a program where a parent process calls fork() to create a child, and the parent immediately calls waitpid() to reap it. Analyze the resulting control flow divergence and convergence.

How many output lines does this program generate and what is the ordering principle?

Solution:
The program generates 2 output lines. The ordering is strictly deterministic: the child's output must appear before the parent's final output because waitpid() acts as a synchronization barrier, forcing the parent's sequential flow to pause until the child's exceptional exit state is processed.

Required Output Task: Analyze the global-waitprob1.c execution flow (approx. 200 words).

Solution:
The execution of global-waitprob1.c serves as a textbook illustration of Exceptional Control Flow through process management. Upon reaching the fork() call at address a_k, the system state undergoes a profound transition. The operating system creates a duplicate logical control flow—the child—which begins its own sequence starting from a duplicate set of registers and address space. This creates a divergence where two distinct sequences (a_0...a_n) coexist. The parent process immediately encounters the waitpid() system call, which is a 'Trap' class exception. This call effectively places the parent's sequential instruction stream in a suspended state, waiting for a hardware-triggered event: the child's termination. In this moment, the child process executes its unique path independently. When the child calls exit(), an exceptional event occurs that notifies the kernel. The kernel then context-switches back to the parent, resolving the waitpid() block. This synchronization barrier ensures that the child's logical flow is 'reaped' before the parent proceeds. Ultimately, the two flows, though briefly concurrent and independent, are reconciled by the OS to ensure predictable output, proving that ECF is not chaotic but a highly structured collaboration between the hardware, kernel, and application logic.